Skip to content

Restructure some pages to create new "Connecting" section#633

Open
peter-smith-phd wants to merge 3 commits intomainfrom
doc-58-docs-restructuring-connecting-to-localstack
Open

Restructure some pages to create new "Connecting" section#633
peter-smith-phd wants to merge 3 commits intomainfrom
doc-58-docs-restructuring-connecting-to-localstack

Conversation

@peter-smith-phd
Copy link
Copy Markdown
Contributor

@peter-smith-phd peter-smith-phd commented May 5, 2026

Summary

To better align with how the customers use our product, this PR creates a new top-level "Connecting" section. This section contains all the necessary documentation for an AWS user to learn how their existing tools (CLI, SDK, IaC) can be configured to work with LocalStack. This section does not introduce any LocalStack-specific features, but purely focuses on how existing tools can be used with LocalStack (which for many users is all they care about).

There have been (almost) no changes to existing pages, but rather the left-hand navigation has been modified to reflect the new structure.

Adds a new top-level Connecting section that groups the docs a user needs to point an existing AWS application at LocalStack:

  • AWS CLI — moved from integrations/aws-native-tools/
  • AWS SDKs — moved from integrations/aws-sdks/; page titles renamed to AWS's official names (e.g. "AWS SDK for .NET")
  • Infrastructure as Code — Terraform, AWS SAM, AWS CDK, Serverless Framework, Pulumi, AWS Chalice, AWS Copilot CLI, Crossplane, Cloud Custodian, Former2 (sidebar order matches that)
  • LocalStack Console — Resource Browser and Stack Overview.
  • IDE Extensions — VS Code Toolkit moved from tooling/, and introduction of new AWS Toolkit page.

All existing pages have been updated to correctly link to these new pages, and redirects have been added/adjusted.

Linear: DOC-58

🤖 Generated with Claude Code

Add a new top-level "Connecting" section grouping the docs needed to
point an existing AWS application at LocalStack — AWS CLI, AWS SDKs,
Infrastructure as Code, LocalStack Console, and the LocalStack
Toolkit (IDEs) — with redirects, updated cross-references, and new
Overview pages.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented May 5, 2026

Deploying localstack-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: af4f8ad
Status:🚫  Build failed.

View logs

@peter-smith-phd peter-smith-phd changed the title DOC-58 Restructure docs into Connecting section Restructure some pages to create new "Connecting" section May 5, 2026
Rename the section directory from connecting-to-localstack to
connecting (shorter URL), rename its sidebar group to "IDE
Extensions", and add an "AWS Toolkit for VS Code" page so the
section covers both available IDE extensions.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@@ -0,0 +1,17 @@
---
title: Overview
description: Connect to LocalStack from your IDE — install, configure, run, and inspect LocalStack without leaving your editor.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
description: Connect to LocalStack from your IDE — install, configure, run, and inspect LocalStack without leaving your editor.
description: Connect to LocalStack from your IDE. Install, configure, run, and inspect LocalStack without leaving your editor.

Copy link
Copy Markdown
Collaborator

@quetzalliwrites quetzalliwrites left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work, Peter!

Looking pretty great, amazing contribution. Thanks, Peter... I also love the plug icon for the nav; that was a great call. 🔌

Feedback Summary:

  1. Redirect Files: There are a few more spots you need to hit to properly update our redirects (your changes to public/_redirects covered just one of them 😸). Please go ahead and update the redirects in these two files as well:

    • scripts/redirects/aws_urls.txt
    • scripts/redirects/_redirects
  2. Style Consistency: For consistency, please avoid using em dashes in the documentation. We don't currently use them in our style guide (context: we've a Linear project in progress for the docs style guide release; as it's not live yet, i understand you wouldn't know this), and adding 4–5 pages with them suddenly makes the content look a bit "AI-written."

As soon as these are addressed, I am happy to approve, MERGE, and party with you.


import SectionCards from '../../../../../components/SectionCards.astro';

Use IDE extensions to install, configure, run, and inspect LocalStack alongside the code you are developing — without leaving your editor. The LocalStack Toolkit manages the LocalStack lifecycle from VS Code, and the AWS Toolkit for VS Code lets you browse and operate on the resources running on your LocalStack instance from a familiar AWS-style explorer.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Use IDE extensions to install, configure, run, and inspect LocalStack alongside the code you are developing without leaving your editor. The LocalStack Toolkit manages the LocalStack lifecycle from VS Code, and the AWS Toolkit for VS Code lets you browse and operate on the resources running on your LocalStack instance from a familiar AWS-style explorer.
Use IDE extensions to install, configure, run, and inspect LocalStack alongside the code you are developing, without leaving your editor. The LocalStack Toolkit manages the LocalStack lifecycle from VS Code, and the AWS Toolkit for VS Code lets you browse and operate on the resources running on your LocalStack instance from a familiar AWS-style explorer.

@@ -0,0 +1,23 @@
---
title: Overview
description: Connect to LocalStack using the same AWS tools you already use — CLI, SDKs, IaC, the web console, and IDE integrations.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
description: Connect to LocalStack using the same AWS tools you already use — CLI, SDKs, IaC, the web console, and IDE integrations.
description: Connect to LocalStack using your favorite AWS tools, such as CLI, SDKs, IaC, the web console, and IDE integrations.


import SectionCards from '../../../../components/SectionCards.astro';

If you already run an application on AWS, you almost certainly connect to it through familiar tools — the AWS CLI, an AWS SDK, an Infrastructure as Code tool such as Terraform or AWS CDK, or an IDE plugin. Running that same application against LocalStack means continuing to use those tools; you only need to point them at LocalStack instead of AWS.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you already run an application on AWS, you almost certainly connect to it through familiar tools the AWS CLI, an AWS SDK, an Infrastructure as Code tool such as Terraform or AWS CDK, or an IDE plugin. Running that same application against LocalStack means continuing to use those tools; you only need to point them at LocalStack instead of AWS.
If you already run an application on AWS, you almost certainly connect to it through familiar tools, such as the AWS CLI, an AWS SDK, an Infrastructure as Code tool such as Terraform or AWS CDK, or an IDE plugin. Running that same application against LocalStack means continuing to use those tools; you only need to point them at LocalStack instead of AWS.

@peter-smith-phd
Copy link
Copy Markdown
Contributor Author

Thanks for the review feedback. I made some changes and published a new revision:

  1. I made sure that all em dashes were remove, although I didn't find any more than what you already identified.

  2. I updated the redirects_config.json file, then auto-generated the _redirects file using the provided script (as per the README.md). It didn't seem that I needed to update the aws_urls.txt file, since there weren't any other recent updates that looked anything like my updates (if I'm wrong, please let me know what I should include there - there's only one line that starts with /aws)

A couple of notes:

  • It seems that the existing redirects have mistakes in them, for example: /user-guide/tools/localstack-sdk/python/ and /user-guide/localstack-enterprise/k8s-operator/ both pointed to invalid pages, so I fixed them.
  • But, now the CloudFlare build is failing, and I don't have access to read the logs. Can you grant me access, or perhaps tell me what I did wrong?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants